Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1526

reference
238-tree-1
name
1526
tree-preservation-order

undefined

238-tpo-1
uprn
address-text
point
POINT (-1.005016 50.854742)
geometry
MULTIPOLYGON (((-1.004917 50.854732,-1.004921 50.854751,-1.004935 50.854769,-1.004957 50.854783,-1.004984 50.854792,-1.005015 50.854795,-1.005046 50.854793,-1.005074 50.854784,-1.005096 50.854770,-1.005110 50.854753,-1.005116 50.854733,-1.005111 50.854714,-1.005098 50.854696,-1.005076 50.854682,-1.005048 50.854673,-1.005018 50.854669,-1.004987 50.854672,-1.004959 50.854681,-1.004937 50.854695,-1.004922 50.854712,-1.004917 50.854732)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL